Release v0.0.7 - #13

Findings

• $\color{orange}◎$ Medium R1-F1 .github/workflows/auto-reviewer.yaml:24 Own caller moves to v0.0.7 in the same PR that precedes the tag

R1-F1 - Important, confidence Medium, .github/workflows/auto-reviewer.yaml:24.
Impact: AGENTS.md rule 3 says the own caller moves to the new tag in a separate PR after tagging. This PR moves it before the v0.0.7 tag exists (the PR description says the tag follows on the squash commit). Between the merge and the tag push, uses: ...@v0.0.7 resolves to nothing, so this repository's own Auto Reviewer fails on main and on any PR opened in that window. It also departs from the documented release order.
Evidence: diff.patch changes line 24 from @v0.0.4 to @v0.0.7; the PR body says "The v0.0.7 tag follows on the squash commit"; AGENTS.md Rules 2 and 3. I could not check from here whether the tag already exists.
Suggestion: Tag first, then open a separate PR with the caller and contract test change. If the owner wants the combined release commit, record that as an exception in AGENTS.md and push the tag immediately after the merge.

Target

Target: PR #13 (261112T1045-dev-session -> main)

Base ae5991a57a6babb248d3a441e61dfc6e7ce97cd5, head d5a8750fee8b09c2d2ba5a9d9c9601ad647bb56a, tree 45e1597fd7734b0fc8c7d62ed280ebb59fca7004, boundary range, uncommitted state none, excluded paths none. Range: ae5991a...d5a8750 3 files changed, 8 insertions(+), 4 deletions(-)
Commits:

• d5a8750 Release v0.0.7: date the changelog and move the own caller

Coverage: Self-review, not independent: I read the diff myself and dispatched no reviewer. Files read: identity.txt, log.txt, stat.txt, pr.json, threads.json (empty), diff.patch, plus a grep of the README, CHANGELOG, tests and scripts for tag references. Intent sources: the PR title and description, and AGENTS.md. This is a first review pass; pr.json holds no earlier reviews.

Axis verdicts

Ready with fixes: the content is correct and consistent, but the release order conflicts with AGENTS.md rule 3.

• Intent: FINDINGS - the changelog dating and the caller and test move are done, but the caller move breaks rule 3 (R1-F1).
• System: FINDINGS - until the tag exists, the caller references an unresolved ref (R1-F1).
• Craft: PASS - the caller and the contract test agree on v0.0.7. The new Repository changelog section sits under the correct heading, and the headings are dated.

Set aside, open questions, and review gaps

Set aside:

• README examples at v0.0.4 and v0.0.6: they were already like that before this PR, and AGENTS.md ties the README to the released tag, so I did not raise it here.
• Dating the changelog headings before tagging: AGENTS.md says the date is added when tagging, and the PR does this at release time, so it is consistent.

Open questions: Does the v0.0.7 tag already exist? If it does, R1-F1 drops to a process note.

Review gaps: Tests were not run in this job. CI (validate) is green on the head SHA, as reported by the caller. I did not run the offline checks or the contract checker. No uncheckable items beyond the tag's existence. No strengths to add.